home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group01b.txt
/
000092_icon-group-sender_Fri Jul 6 09:40:09 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2002-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id f66Ge3k19325
for icon-group-addresses; Fri, 6 Jul 2001 09:40:04 -0700 (MST)
Message-Id: <200107061640.f66Ge3k19325@baskerville.CS.Arizona.EDU>
Date: Fri, 6 Jul 2001 16:38:32 +1200 (NZST)
From: "Richard A. O'Keefe" <ok@atlas.otago.ac.nz>
To: art.eschenlauer@sufsys.com, hgs@dmu.ac.uk
Subject: Re: Software testing for Icon?
Cc: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 752
Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> wrote:
I don't know. With Icon not being OO, I'm not sure if one can apply
unit testing to it, but it has been done somehow in C, so maybe...
That's a strange comment. Unit testing has *nothing* to do with OO.
People were unit-testing Fortran and COBOL long before OO was born in 1967.
OO has been pretty disastrous for testing, because you _can't_ test code
thoroughly. The next subclass to come along may wreck everything. (Except
in Eiffel, if you're careful.) It is much much _easier_ to do unit testing
in Icon than in C++ or Java. (Yes, I'm aware of CppUnit. I have it. It
still falls foul of the fact that subclassing means that the code you tested
is not the code your client is running.)